Description

Working to migrate off of NX as a build workflow tool in favor of the built-in system available in Yarn. Why? Fewer additional dependencies and more straight-forward tooling makes onboarding contributors easier. While NX does offer better caching services, yarn has a better user-experience for parallelizing on the command line.

This PR also defines certain constraints for our component packages. Constraints are a feature of Yarn that allows us to define properties for the package.json to keep them aligned and consistent.

How and where has this been tested?

Please tag yourself on the tests you've marked complete to confirm the tests have been run by someone other than the author.

Validation steps

Regression testing

Validate:

1. The documentation pages for at least two other components are still loading, including:

• The pages render correctly, are accessible, and are responsive.

2. If components have been modified, VRTs have been run on this branch:

• VRTs have been run and looked at.
• Any VRT changes have been accepted (by reviewer and/or PR author), or there are no changes.

Screenshots

To-do list

• I have read the contribution guidelines.
• I have updated relevant storybook stories and templates.
• I have tested these changes in Windows High Contrast mode.
• If my change impacts other components, I have tested to make sure they don't break.
• If my change impacts documentation, I have updated the documentation accordingly.
• ✨ This pull request is ready to merge. ✨